SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Flowchart</title>

</head>

Flowchart

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">"Flow chart" redirects here. For the poem, see <a href="Flow_Chart_(poem)" title="Flow Chart (poem)">Flow Chart (poem)</a>. For the music group, see <a href="Flowchart_(band)" title="Flowchart (band)">Flowchart (band)</a>.</div>

A flowchart is a type of <a href="Diagram" title="Diagram">diagram</a> that represents a <a href="Workflow" title="Workflow">workflow</a> or <a href="Process" title="Process">process</a>. A flowchart can also be defined as a diagrammatic representation of an <a href="Algorithm" title="Algorithm">algorithm</a>, a step-by-step approach to solving a task.

The flowchart shows the steps as boxes of various kinds, and their order by connecting the boxes with arrows. This diagrammatic representation illustrates a solution model to a given problem. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.<a href="#cite_note-SSEV-1">[1]</a>

<div class="mw-heading mw-heading2"><h2 id="Overview">Overview</h2></div>

Flowcharts are used to design and document simple processes or programs. Like other types of diagrams, they help visualize the process. Two of the many benefits are that flaws and <a href="Bottleneck_(production)" title="Bottleneck (production)">bottlenecks</a> may become apparent. Flowcharts typically use the following main symbols:

<ul><li>A process step, usually called an activity, is denoted by a rectangular box.</li>

<li>A decision is usually denoted by a diamond.</li></ul>

A flowchart is described as "cross-functional" when the chart is divided into different vertical or horizontal parts, to describe the control of different organizational units. A symbol appearing in a particular part is within the control of that organizational unit. A cross-functional flowchart allows the author to correctly locate the responsibility for performing an action or making a decision, and to show the responsibility of each organizational unit for different parts of a single process.

Flowcharts represent certain aspects of processes and are usually complemented by other types of diagram. For instance, <a href="Kaoru_Ishikawa" title="Kaoru Ishikawa">Kaoru Ishikawa</a> defined the flowchart as one of the <a href="Seven_basic_tools_of_quality" title="Seven basic tools of quality">seven basic tools of quality control</a>, next to the <a href="Histogram" title="Histogram">histogram</a>, <a href="Pareto_chart" title="Pareto chart">Pareto chart</a>, <a href="Check_sheet" title="Check sheet">check sheet</a>, <a href="Control_chart" title="Control chart">control chart</a>, <a href="Ishikawa_diagram" title="Ishikawa diagram">cause-and-effect diagram</a>, and the <a href="Scatter_diagram" class="mw-redirect" title="Scatter diagram">scatter diagram</a>. Similarly, in <a href="Unified_Modeling_Language" title="Unified Modeling Language">UML</a>, a standard concept-modeling notation used in software development, the <a href="Activity_diagram" title="Activity diagram">activity diagram</a>, which is a type of flowchart, is just one of many different diagram types.

<a href="Nassi-Shneiderman_diagram" class="mw-redirect" title="Nassi-Shneiderman diagram">Nassi-Shneiderman diagrams</a> and <a href="DRAKON" title="DRAKON">Drakon-charts</a> are an alternative notation for process flow.

Common alternative names include: flow chart, process flowchart, functional flowchart, process map, process chart, functional process chart, business process model, process model, process <a href="Flow_diagram" title="Flow diagram">flow diagram</a>, <a href="Workflow" title="Workflow">work flow</a> diagram, business flow diagram. The terms "flowchart" and "flow chart" are used interchangeably.

The underlying <a href="Graph_(discrete_mathematics)" title="Graph (discrete mathematics)">graph</a> structure of a flowchart is a flow graph, which abstracts away node types, their contents and other ancillary information.

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

The first structured method for documenting process flow, the "<a href="Flow_process_chart" title="Flow process chart">flow process chart</a>", was introduced by <a href="Frank_Bunker_Gilbreth" title="Frank Bunker Gilbreth">Frank</a> and <a href="Lillian_Moller_Gilbreth" title="Lillian Moller Gilbreth">Lillian Gilbreth</a> in the presentation "Process Charts: First Steps in Finding the One Best Way to do Work", to members of the <a href="American_Society_of_Mechanical_Engineers" title="American Society of Mechanical Engineers">American Society of Mechanical Engineers (ASME)</a> in 1921.<a href="#cite_note-2">[2]</a> The Gilbreths' tools quickly found their way into <a href="Industrial_engineering" title="Industrial engineering">industrial engineering</a> curricula. In the early 1930s, an industrial engineer, <a href="Allan_H._Mogensen" title="Allan H. Mogensen">Allan H. Mogensen</a> began to train business people in the use of some of the tools of industrial engineering at his Work Simplification Conferences in <a href="Lake_Placid%2C_New_York" title="Lake Placid, New York">Lake Placid</a>, <a href="New_York_(state)" title="New York (state)">New York</a>.

Art Spinanger, a 1944 graduate of <a href="Allan_H._Mogensen" title="Allan H. Mogensen">Mogensen</a>'s class, took the tools back to <a href="Procter_and_Gamble" class="mw-redirect" title="Procter and Gamble">Procter and Gamble</a> where he developed their Deliberate Methods Change Program. <a href="Benjamin_S._Graham" title="Benjamin S. Graham">Ben S. Graham</a>, another 1944 graduate, Director of Formcraft Engineering at <a href="Standard_Register_Industrial" class="mw-redirect" title="Standard Register Industrial">Standard Register Industrial</a>, applied the flow process chart to information processing with his development of the multi-flow process chart, to present multiple documents and their relationships.<a href="#cite_note-3">[3]</a> In 1947, <a href="ASME" class="mw-redirect" title="ASME">ASME</a> adopted a symbol set derived from Gilbreth's original work as the "ASME Standard: Operation and Flow Process Charts."<a href="#cite_note-4">[4]</a>

<a href="Douglas_Hartree" title="Douglas Hartree">Douglas Hartree</a> in 1949 explained that <a href="Herman_Goldstine" title="Herman Goldstine">Herman Goldstine</a> and <a href="John_von_Neumann" title="John von Neumann">John von Neumann</a> had developed a flowchart (originally, diagram) to plan computer programs.<a href="#cite_note-5">[5]</a> His contemporary account was endorsed by IBM engineers<a href="#cite_note-6">[6]</a> and by Goldstine's personal recollections.<a href="#cite_note-7">[7]</a> The original programming flowcharts of Goldstine and von Neumann can be found in their unpublished report, "Planning and coding of problems for an electronic computing instrument, Part II, Volume 1" (1947), which is reproduced in von Neumann's collected works.<a href="#cite_note-8">[8]</a>

The flowchart became a popular tool for describing <a href="Computer_algorithm" class="mw-redirect" title="Computer algorithm">computer algorithms</a>, but its popularity decreased in the 1970s, when interactive <a href="Computer_terminal" title="Computer terminal">computer terminals</a> and <a href="Third-generation_programming_language" title="Third-generation programming language">third-generation programming languages</a> became common tools for <a href="Computer_programming" title="Computer programming">computer programming</a>, since algorithms can be expressed more concisely as <a href="Source_code" title="Source code">source code</a> in such <a href="Programming_language" title="Programming language">languages</a>. Often <a href="Pseudo-code" class="mw-redirect" title="Pseudo-code">pseudo-code</a> is used, which uses the common idioms of such languages without strictly adhering to the details of a particular one. Also, flowcharts are not well-suited for new programming techniques such as <a href="Recursion_(computer_science)" title="Recursion (computer science)">recursive programming</a>.

Nevertheless, flowcharts were still used in the early 21st century for describing <a href="Computer_algorithm" class="mw-redirect" title="Computer algorithm">computer algorithms</a>.<a href="#cite_note-9">[9]</a> Some techniques such as <a href="Unified_Modeling_Language" title="Unified Modeling Language">UML</a> <a href="Activity_diagram" title="Activity diagram">activity diagrams</a> and <a href="DRAKON" title="DRAKON">Drakon-charts</a> can be considered to be extensions of the flowchart.

<div class="mw-heading mw-heading2"><h2 id="Types">Types</h2></div>

Sterneckert (2003) suggested that flowcharts can be modeled from the perspective of different user groups (such as managers, system analysts and clerks), and that there are four general types:<a href="#cite_note-Ster03-10">[10]</a>

<ul><li>Document flowcharts, showing controls over a document-flow through a system</li>

<li>Data flowcharts, showing controls over a data-flow in a system</li>

<li>System flowcharts, showing controls at a physical or resource level</li>

<li>Program flowchart, showing the controls in a program within a system</li></ul>

Notice that every type of flowchart focuses on some kind of control, rather than on the particular flow itself.<a href="#cite_note-Ster03-10">[10]</a>

However, there are some different classifications. For example, Andrew Veronis (1978) named three basic types of flowcharts: the system flowchart, the general flowchart, and the detailed flowchart.<a href="#cite_note-11">[11]</a> That same year Marilyn Bohl (1978) stated "in practice, two kinds of flowcharts are used in solution planning: system flowcharts and program flowcharts...".<a href="#cite_note-12">[12]</a> More recently, Mark A. Fryman (2001) identified more differences: "Decision flowcharts, logic flowcharts, systems flowcharts, product flowcharts, and process flowcharts are just a few of the different types of flowcharts that are used in business and government".<a href="#cite_note-13">[13]</a>

In addition, many diagram techniques are similar to flowcharts but carry a different name, such as <a href="Unified_Modeling_Language" title="Unified Modeling Language">UML</a> <a href="Activity_diagram" title="Activity diagram">activity diagrams</a>.

Reversible flowcharts<a href="#cite_note-14">[14]</a> represent a paradigm in computing that focuses on the reversibility of computational processes. Unlike traditional computing models, where operations are often irreversible, reversible flowcharts ensure that any atomic computational step can be reversed. Reversible flowcharts are shown to be as expressive as reversible Turing machines, and are a theoretical foundation for <a href="Janus_(time-reversible_computing_programming_language)" title="Janus (time-reversible computing programming language)">structured reversible programming</a> and energy-efficient reversible computing systems.<a href="#cite_note-15">[15]</a>

<div class="mw-heading mw-heading2"><h2 id="Building_blocks">Building blocks</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Common_symbols">Common symbols</h3></div>

The <a href="American_National_Standards_Institute" title="American National Standards Institute">American National Standards Institute</a> (ANSI) set standards for flowcharts and their symbols in the 1960s.<a href="#cite_note-ShellyVermaat2011-16">[16]</a> The <a href="International_Organization_for_Standardization" title="International Organization for Standardization">International Organization for Standardization</a> (ISO) adopted the ANSI symbols in 1970.<a href="#cite_note-Myler1998-17">[17]</a> The current standard, ISO 5807, was published in 1985 and last reviewed in 2019.<a href="#cite_note-18">[18]</a> Generally, flowcharts flow from top to bottom and left to right.<a href="#cite_note-IBM1970-19">[19]</a>

<th>ANSI/ISO Shape

</th>

<th>Name

</th>

<th>Description

</th></tr>

<tr>

</td>

<td style="text-align: center;">Flowline (arrowhead)<a href="#cite_note-Myler1998-17">[17]</a>

</td>

<td>Shows the process's order of operation. A line coming from one symbol and pointing at another.<a href="#cite_note-ShellyVermaat2011-16">[16]</a> Arrowheads are added if the flow is not the standard top-to-bottom, left-to right.<a href="#cite_note-Myler1998-17">[17]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">Terminal<a href="#cite_note-ShellyVermaat2011-16">[16]</a>

</td>

<td>Indicates the beginning and ending of a program or sub-process. Represented as a <a href="Stadium_(geometry)" title="Stadium (geometry)">stadium</a>,<a href="#cite_note-ShellyVermaat2011-16">[16]</a> oval or rounded (fillet) rectangle. They usually contain the word "Start" or "End", or another phrase signaling the start or end of a process, such as "submit inquiry" or "receive product".

</td></tr>

<tr>

</td>

<td style="text-align: center;">Process<a href="#cite_note-Myler1998-17">[17]</a>

</td>

<td>Represents a set of operations that changes value, form, or location of data. Represented as a <a href="Rectangle" title="Rectangle">rectangle</a>.<a href="#cite_note-Myler1998-17">[17]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">Decision<a href="#cite_note-Myler1998-17">[17]</a>

</td>

<td>Shows a conditional operation that determines which one of the two paths the program will take.<a href="#cite_note-ShellyVermaat2011-16">[16]</a> The operation is commonly a yes/no question or true/false test. Represented as a diamond (<a href="Rhombus" title="Rhombus">rhombus</a>).<a href="#cite_note-Myler1998-17">[17]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">Input/output<a href="#cite_note-Myler1998-17">[17]</a>

</td>

<td>Indicates the process of inputting and outputting data,<a href="#cite_note-Myler1998-17">[17]</a> as in entering data or displaying results. Represented as a <a href="Rhomboid" title="Rhomboid">rhomboid</a>.<a href="#cite_note-ShellyVermaat2011-16">[16]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">Annotation<a href="#cite_note-ShellyVermaat2011-16">[16]</a> (comment)<a href="#cite_note-Myler1998-17">[17]</a>

</td>

<td>Indicating additional information about a step in the program. Represented as an open rectangle with a dashed or solid line connecting it to the corresponding symbol in the flowchart.<a href="#cite_note-Myler1998-17">[17]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">Predefined process<a href="#cite_note-ShellyVermaat2011-16">[16]</a>

</td>

<td>Shows named process which is defined elsewhere. Represented as a rectangle with double-struck vertical edges.<a href="#cite_note-ShellyVermaat2011-16">[16]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">On-page connector<a href="#cite_note-ShellyVermaat2011-16">[16]</a>

</td>

<td>Pairs of labeled connectors replace long or confusing lines on a flowchart page. Represented by a small circle with a letter inside.<a href="#cite_note-ShellyVermaat2011-16">[16]</a><a href="#cite_note-RFF-20">[20]</a>

</td></tr>

<tr>

</td>

<td style="text-align: center;">Off-page connector<a href="#cite_note-ShellyVermaat2011-16">[16]</a>

</td>

<td>A labeled connector for use when the target is on another page. Represented as a <a href="Baseball_field#Home_base" title="Baseball field">home plate</a>-shaped <a href="Pentagon" title="Pentagon">pentagon</a>.<a href="#cite_note-ShellyVermaat2011-16">[16]</a><a href="#cite_note-RFF-20">[20]</a>

</td></tr></tbody></table>

<div class="mw-heading mw-heading3"><h3 id="Other_symbols">Other symbols</h3></div>

The ANSI/ISO standards include symbols beyond the basic shapes. Some are:<a href="#cite_note-IBM1970-19">[19]</a><a href="#cite_note-RFF-20">[20]</a>

<th>Shape

</th>

<th>Name

</th>

<th>Description

</th></tr>

<tr>

</td>

<td style="text-align: center;">Data File or Database

</td>

<td>Data represented by a <a href="Cylinder" title="Cylinder">cylinder</a> symbolizing a disk drive.

</td></tr>

<tr>

</td>

<td rowspan="2" style="text-align: center;">Document

</td>

<td>Single documents represented as a <a href="Rectangle" title="Rectangle">rectangle</a> with a wavy base.

</td></tr>

<tr>

</td>

<td>Multiple documents represented as a stack of rectangles with wavy bases.

</td></tr>

<tr>

</td>

<td style="text-align: center;">Manual operation

</td>

<td>Represented by a <a href="Trapezoid" title="Trapezoid">trapezoid</a> with the longest parallel side at the top, to represent an operation or adjustment to process that can only be made manually.

</td></tr>

<tr>

<td>

</td>

<td style="text-align: center;">Manual input

</td>

<td>Represented by <a href="Quadrilateral" title="Quadrilateral">quadrilateral</a>, with the top irregularly sloping up from left to right, like the side view of a <a href="Computer_keyboard" title="Computer keyboard">keyboard</a>.

</td></tr>

<tr>

</td>

<td style="text-align: center;">Preparation or Initialization

</td>

<td>Represented by an elongated <a href="Hexagon" title="Hexagon">hexagon</a>, originally used for steps like setting a switch or initializing a routine.

</td></tr></tbody></table>

<div class="mw-heading mw-heading3"><h3 id="Parallel_processing">Parallel processing</h3></div>

<ul><li><a href="Parallel_computing" title="Parallel computing">Parallel Mode</a> is represented by two horizontal lines at the beginning or ending of simultaneous operations<a href="#cite_note-IBM1970-19">[19]</a></li></ul>

For <a href="Parallel_computing" title="Parallel computing">parallel</a> and <a href="Concurrent_computing" title="Concurrent computing">concurrent</a> processing the Parallel Mode horizontal lines<a href="#cite_note-Valvano2011-21">[21]</a> or a horizontal bar<a href="#cite_note-Nakatsu2009-22">[22]</a> indicate the start or end of a section of processes that can be done independently:

<ul><li>At a <a href="Fork%E2%80%93join_model" title="Fork–join model">fork</a>, the process creates one or more additional processes, indicated by a bar with one incoming path and two or more outgoing paths.</li>

<li>At a join, two or more processes continue as a single process, indicated by a bar with several incoming paths and one outgoing path. All processes must complete before the single process continues.<a href="#cite_note-Nakatsu2009-22">[22]</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Diagramming_software">Diagramming software</h2></div>

Any drawing program can be used to create flowchart diagrams, but these will have no underlying data model to share data with databases or other programs such as <a href="Project_management" title="Project management">project management</a> systems or <a href="Spreadsheet" title="Spreadsheet">spreadsheet</a>. Many software packages exist that can create flowcharts automatically, either directly from a programming language source code, or from a flowchart description language.

There are several applications and <a href="Visual_programming_languages" class="mw-redirect" title="Visual programming languages">visual programming languages</a><a href="#cite_note-23">[23]</a> that use flowcharts to represent and execute programs. Generally these are used as teaching tools for beginner students.

/* start https://en.wikipedia.org/ */

.mw-parser-output .col-begin{border-collapse:collapse;padding:0;color:inherit;width:100%;border:0;margin:0}.mw-parser-output .col-begin-small{font-size:90%}.mw-parser-output .col-break{vertical-align:top;text-align:left}.mw-parser-output .col-break-2{width:50%}.mw-parser-output .col-break-3{width:33.3%}.mw-parser-output .col-break-4{width:25%}.mw-parser-output .col-break-5{width:20%}@media(max-width:720px){.mw-parser-output .col-begin,.mw-parser-output .col-begin>tbody,.mw-parser-output .col-begin>tbody>tr,.mw-parser-output .col-begin>tbody>tr>td{display:block!important;width:100%!important}.mw-parser-output .col-break{padding-left:0!important}}

/* end https://en.wikipedia.org/ */

</style><div>

<div class="mw-heading mw-heading3"><h3 id="Related_diagrams">Related diagrams</h3></div>

<ul><li><a href="Activity_diagram" title="Activity diagram">Activity diagram</a></li>

<li><a href="Control-flow_diagram" title="Control-flow diagram">Control-flow diagram</a></li>

<li><a href="Control-flow_graph" title="Control-flow graph">Control-flow graph</a></li>

<li><a href="Data_flow_diagram" class="mw-redirect" title="Data flow diagram">Data flow diagram</a></li>

<li><a href="Deployment_flowchart" title="Deployment flowchart">Deployment flowchart</a></li>

<li><a href="DRAKON" title="DRAKON">Drakon-chart</a></li>

<li><a href="Functional_flow_block_diagram" title="Functional flow block diagram">Functional flow block diagram</a></li>

<li><a href="Nassi%E2%80%93Shneiderman_diagram" title="Nassi–Shneiderman diagram">Nassi–Shneiderman diagram</a></li>

<li><a href="State_diagram" title="State diagram">State diagram</a></li>

<li><a href="Swimlane" title="Swimlane">Swimlane</a></li>

<li><a href="Warnier/Orr_diagram" title="Warnier/Orr diagram">Warnier/Orr diagram</a></li>

<li><a href="Why-because_analysis" class="mw-redirect" title="Why-because analysis">Why-because analysis</a></li></ul>

</td>

<div class="mw-heading mw-heading3"><h3 id="Related_subjects">Related subjects</h3></div>

<ul><li><a href="Augmented_transition_network" title="Augmented transition network">Augmented transition network</a></li>

<li><a href="Business_process_mapping" title="Business process mapping">Business process mapping</a></li>

<li><a href="Data_and_information_visualization" title="Data and information visualization">Data and information visualization</a></li>

<li><a href="Interactive_EasyFlow" title="Interactive EasyFlow">Interactive EasyFlow</a></li>

<li><a href="Process_architecture" title="Process architecture">Process architecture</a></li>

<li><a href="Pseudocode" title="Pseudocode">Pseudocode</a></li>

<li><a href="Recursive_transition_network" title="Recursive transition network">Recursive transition network</a></li>

<li><a href="Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a> (UML)</li>

<li><a href="Workflow" title="Workflow">Workflow</a></li></ul>

</td></tr></tbody></table></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width reflist-columns-2">

<li id="cite_note-SSEV-1"><a href="#cite_ref-SSEV_1-0">^</a> <a rel="nofollow" class="external text" href="http://pascal.computer.org/sev_display/index.action">SEVOCAB: Software Systems Engineering Vocabulary</a>. Term: Flow chart. Retrieved 31 July 2008.

</li>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFGilbrethGilbreth1921" class="citation web cs1">Gilbreth, Frank Bunker; Gilbreth, Lillian Moller (1921). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20150509222833/https://engineering.purdue.edu/IE/GilbrethLibrary/gilbrethproject/processcharts.pdf">"Process Charts"</a> (PDF). Archived from <a rel="nofollow" class="external text" href="https://engineering.purdue.edu/IE/GilbrethLibrary/gilbrethproject/processcharts.pdf">the original</a> (PDF) on 2015-05-09. Retrieved 2016-05-06.</cite>. American Society of Mechanical Engineers.

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite id="CITEREFGraham1996" class="citation web cs1">Graham, Ben S. Jr. (10 June 1996). <a rel="nofollow" class="external text" href="http://www.worksimp.com/articles/keynoteworkflowcanada.htm">"People come first"</a>. Keynote Address at Workflow Canada.</cite>

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> American Society of Mechanical Engineers (1947) ASME standard; operation and flow process charts. New York, 1947. (<a rel="nofollow" class="external text" href="http://catalog.hathitrust.org/Record/005735891">online version</a>)

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite id="CITEREFHartree1949" class="citation book cs1"><a href="Douglas_Rayner_Hartree" class="mw-redirect" title="Douglas Rayner Hartree">Hartree, Douglas</a> (1949). <a rel="nofollow" class="external text" href="https://archive.org/stream/calculatinginstr00doug#page/112/mode/2up">Calculating Instruments and Machines</a>. The University of Illinois Press. p. 112.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite id="CITEREFBashe1986" class="citation book cs1">Bashe, Charles (1986). <a rel="nofollow" class="external text" href="https://archive.org/details/ibmsearlycompute00bash">IBM's Early Computers</a>. The MIT Press. p. <a rel="nofollow" class="external text" href="https://archive.org/details/ibmsearlycompute00bash/page/327">327</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780262022255</bdi>.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFGoldstine1972" class="citation book cs1"><a href="Herman_H._Goldstine" class="mw-redirect" title="Herman H. Goldstine">Goldstine, Herman</a> (1972). <a rel="nofollow" class="external text" href="https://archive.org/details/computerfrompasc00herm/page/266">The Computer from Pascal to Von Neumann</a>. Princeton University Press. pp. <a rel="nofollow" class="external text" href="https://archive.org/details/computerfrompasc00herm/page/266">266–267</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-691-08104-2</bdi>.</cite>

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite id="CITEREFTaub1963" class="citation book cs1"><a href="Abraham_Haskel_Taub" class="mw-redirect" title="Abraham Haskel Taub">Taub, Abraham</a> (1963). John von Neumann Collected Works. Vol. 5. Macmillan. pp. 80–151.</cite>

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> Bohl, Rynn: "Tools for Structured and Object-Oriented Design", Prentice Hall, 2007.

</li>

<li id="cite_note-Ster03-10">^ <a href="#cite_ref-Ster03_10-0">a</a> <a href="#cite_ref-Ster03_10-1">b</a> Alan B. Sterneckert (2003) Critical Incident Management. <a rel="nofollow" class="external text" href="https://books.google.com/books?id=8z93xStbEpAC&pg=PA126">p. 126</a>

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> Andrew Veronis (1978) Microprocessors: Design and Applications. <a rel="nofollow" class="external text" href="https://books.google.com/books?id=GZ9QAAAAMAAJ&q=%22three+basic+types+of+flowcharts+%28ie,+the+system+flowchart,+the+general+flowchart,+and+the+detailed+flowchart%29.%22">p. 111</a>

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> Marilyn Bohl (1978) A Guide for Programmers. p. 65.

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> Mark A. Fryman (2001) Quality and Process Improvement. <a rel="nofollow" class="external text" href="https://books.google.com/books?id=M-_B7czAy0kC&pg=PA169">p. 169</a>.

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <cite id="CITEREFYokoyamaAxelsenGlück2016" class="citation journal cs1">Yokoyama, Tetsuo; Axelsen, Holger Bock; Glück, Robert (January 2016). <a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.tcs.2015.07.046">"Fundamentals of reversible flowchart languages"</a>. Theoretical Computer Science. 611: 87–115. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.tcs.2015.07.046">10.1016/j.tcs.2015.07.046</a>.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite id="CITEREFKrakovsky2021" class="citation journal cs1">Krakovsky, Marina (June 2021). <a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F3460214">"Taking the heat"</a>. Communications of the ACM. 64 (6): 18–20. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F3460214">10.1145/3460214</a>.</cite>

</li>

<li id="cite_note-ShellyVermaat2011-16">^ <a href="#cite_ref-ShellyVermaat2011_16-0">a</a> <a href="#cite_ref-ShellyVermaat2011_16-1">b</a> <a href="#cite_ref-ShellyVermaat2011_16-2">c</a> <a href="#cite_ref-ShellyVermaat2011_16-3">d</a> <a href="#cite_ref-ShellyVermaat2011_16-4">e</a> <a href="#cite_ref-ShellyVermaat2011_16-5">f</a> <a href="#cite_ref-ShellyVermaat2011_16-6">g</a> <a href="#cite_ref-ShellyVermaat2011_16-7">h</a> <a href="#cite_ref-ShellyVermaat2011_16-8">i</a> <a href="#cite_ref-ShellyVermaat2011_16-9">j</a> <a href="#cite_ref-ShellyVermaat2011_16-10">k</a> <a href="#cite_ref-ShellyVermaat2011_16-11">l</a> <a href="#cite_ref-ShellyVermaat2011_16-12">m</a> <cite id="CITEREFGary_B._ShellyMisty_E._Vermaat2011" class="citation book cs1">Gary B. Shelly; Misty E. Vermaat (2011). <a rel="nofollow" class="external text" href="https://archive.org/details/discoveringcompu00shel_187">Discovering Computers, Complete: Your Interactive Guide to the Digital World</a>. Cengage Learning. pp. <a rel="nofollow" class="external text" href="https://archive.org/details/discoveringcompu00shel_187/page/n716">691</a>–693. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-111-53032-7</bdi>.</cite>

</li>

<li id="cite_note-Myler1998-17">^ <a href="#cite_ref-Myler1998_17-0">a</a> <a href="#cite_ref-Myler1998_17-1">b</a> <a href="#cite_ref-Myler1998_17-2">c</a> <a href="#cite_ref-Myler1998_17-3">d</a> <a href="#cite_ref-Myler1998_17-4">e</a> <a href="#cite_ref-Myler1998_17-5">f</a> <a href="#cite_ref-Myler1998_17-6">g</a> <a href="#cite_ref-Myler1998_17-7">h</a> <a href="#cite_ref-Myler1998_17-8">i</a> <a href="#cite_ref-Myler1998_17-9">j</a> <a href="#cite_ref-Myler1998_17-10">k</a> <cite id="CITEREFHarley_R._Myler1998" class="citation book cs1">Harley R. Myler (1998). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=IisfMsdBe2IC&pg=PA32">"2.3 Flowcharts"</a>. Fundamentals of Engineering Programming with C and Fortran. Cambridge University Press. pp. 32–36. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-521-62950-8</bdi>.</cite>

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.iso.org/standard/11955.html">"ISO 5807:1985: Information processing — Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts"</a>. International Organization for Standardization. February 1985. Retrieved 23 July 2017.</cite>

</li>

<li id="cite_note-IBM1970-19">^ <a href="#cite_ref-IBM1970_19-0">a</a> <a href="#cite_ref-IBM1970_19-1">b</a> <a href="#cite_ref-IBM1970_19-2">c</a> <cite class="citation book cs1"><a rel="nofollow" class="external text" href="https://fulmanski.pl/zajecia/wdi/zajecia_20142015/materialy/IBM-FlowchartingTechniques-GC20-8152-1.pdf">Flowcharting Techniques GC20-8152-1</a> (PDF). IBM. March 1970. p. 10. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20211015061455/https://fulmanski.pl/zajecia/wdi/zajecia_20142015/materialy/IBM-FlowchartingTechniques-GC20-8152-1.pdf">Archived</a> (PDF) from the original on 2021-10-15.</cite>

</li>

<li id="cite_note-RFF-20">^ <a href="#cite_ref-RFF_20-0">a</a> <a href="#cite_ref-RFF_20-1">b</a> <a href="#cite_ref-RFF_20-2">c</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.rff.com/flowchart_shapes.php">"What do the different flowchart shapes mean?"</a>. RFF Electronics. Retrieved 23 July 2017.</cite>

</li>

<li id="cite_note-Valvano2011-21"><a href="#cite_ref-Valvano2011_21-0">^</a> <cite id="CITEREFJonathan_W._Valvano2011" class="citation book cs1">Jonathan W. Valvano (2011). Embedded Microcomputer Systems: Real Time Interfacing. Cengage Learning. pp. 131–132. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-111-42625-5</bdi>.</cite>

</li>

<li id="cite_note-Nakatsu2009-22">^ <a href="#cite_ref-Nakatsu2009_22-0">a</a> <a href="#cite_ref-Nakatsu2009_22-1">b</a> <cite id="CITEREFRobbie_T._Nakatsu2009" class="citation book cs1">Robbie T. Nakatsu (2009). Reasoning with Diagrams: Decision-Making and Problem-Solving with Diagrams. John Wiley & Sons. pp. 68–69. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-470-40072-2</bdi>.</cite>

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> Myers, Brad A. "<a rel="nofollow" class="external text" href="https://www.cs.cmu.edu/~bam/papers/chi86vltax.pdf">Visual programming, programming by example, and program visualization: a taxonomy.</a>" ACM SIGCHI Bulletin. Vol. 17. No. 4. ACM, 1986.

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li><cite id="CITEREFISO_58071985" class="citation book cs1">ISO 5807 (1985). <a rel="nofollow" class="external text" href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=11955">Information processing – Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts</a>. International Organization for Standardization.</cite><code class="cs1-code">{{cite book}}</code>: CS1 maint: numeric names: authors list (link)</li>

<li><a href="ISO_10628" title="ISO 10628">ISO 10628</a>: Diagrams for the chemical and petrochemical industry</li>

<li><a rel="nofollow" class="external text" href="http://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/ECMA-4,%202nd%20Edition,%20September%201966.pdf">ECMA 4: Flowcharts</a> (withdrawn – <a rel="nofollow" class="external text" href="http://www.ecma-international.org/publications/standards/Standardwithdrawn.htm">list</a> of withdrawn standards)</li>

<li><a href="Schultheiss%2C_Louis_A." class="mw-redirect" title="Schultheiss, Louis A.">Schultheiss, Louis A.</a>, and Edward M. Heiliger. "<a rel="nofollow" class="external text" href="https://www.ideals.illinois.edu/bitstream/handle/2142/743/1963Schultheiss.pdf?sequence=2">Techniques of flow-charting</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210714184641/https://www.ideals.illinois.edu/bitstream/handle/2142/743/1963Schultheiss.pdf?sequence=2">Archived</a> 2021-07-14 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>." (1963); with introduction by Edward Heiliger.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <a href="https://commons.wikimedia.org/wiki/Flow_chart" class="extiw external" title="commons:Flow chart">Flow chart</a>.</div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120402204237/http://www.fh-jena.de/~kleine/history/software/IBM-FlowchartingTechniques-GC20-8152-1.pdf">Flowcharting Techniques</a>: An IBM manual from 1969 (5 MB; PDF)</li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="International_Organization_for_Standardization_(ISO)_standards364" style="padding:3px"><table class="nowraplinks hlist mw-collapsible mw-collapsed navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="International_Organization_for_Standardization_(ISO)_standards364" style="font-size:114%;margin:0 4em"><a href="International_Organization_for_Standardization" title="International Organization for Standardization">International Organization for Standardization</a> (ISO) standards</div></th></tr><tr><td class="navbox-abovebelow" colspan="2"><div>List of <a href="List_of_ISO_standards" title="List of ISO standards">ISO standards</a> – <a href="List_of_ISO_romanizations" title="List of ISO romanizations">ISO romanizations</a> – <a href="List_of_IEC_standards" title="List of IEC standards">IEC standards</a></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">1–9999</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">10000–19999</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">20000–29999</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="ISO/IEC_27000_family" title="ISO/IEC 27000 family">27000 series</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">30000+</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li> Category</li></ul>

</div></td></tr></tbody></table></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q185092#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata1559" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q185092#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata1559" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4131768-3">Germany</a></li><li><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh85049286">United States</a></li><li><a rel="nofollow" class="external text" href="https://catalogue.bnf.fr/ark:/12148/cb11940186h">France</a></li><li><a rel="nofollow" class="external text" href="https://data.bnf.fr/ark:/12148/cb11940186h">BnF data</a></li><li><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph127478&CON_LNG=ENG">Czech Republic</a></li><li><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007538452105171">Israel</a></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://catalog.archives.gov/id/10628870">NARA</a></li><li><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/bde747b9-e1ff-46cb-ae91-f327bb71447f">Yale LUX</a></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-22" href="https://en.wikipedia.org/wiki/?title=Flowchart&oldid=1301857814">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>